Methods, apparatuses and computer program products for generating logistics zones

ABSTRACT

An apparatus is provided for generating logistics zones. The apparatus may include at least one memory and at least one processor configured to generate logistics zones responsive to receipt of a selection of a geographic area. The logistics zones are generated based on street segment attribute data. The logistics zones include a geo-fenced right zone on a right side of corresponding street segments and a geo-fenced left zone on a left side of the street segments. The processor is also configured to determine addresses in the logistics zones based on analyzing the street segment attribute data. The processor is further configured to generate a route for delivery or pickup of packages within the logistics zones based on a trace order of the logistics zones specifying a sequential order to travel within the logistics zones responsive to determining a shortest travel path. Corresponding computer program products and methods are also provided.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/964,766, filed Dec. 8, 2013, the contents of which is herebyincorporated herein in its entirety by reference.

TECHNOLOGICAL FIELD

Embodiments of the invention relate generally to generating logisticszones and more generally relate to methods, apparatuses and computerprogram products for utilizing the logistics zones to facilitatedelivery and/or pickup of packages.

BACKGROUND

Currently, shipping carriers develop dispatch plans for the delivery ofpackages based on delivery stops on individual streets. However, in someinstances this may not be the most efficient manner in which to deliverpackages. For instance, there may be multiple deliveries in a particulararea for delivery stops that are on different streets and as such thedispatch plan may not be optimized for delivery of the packages in thearea. For example, the dispatch plan may designate to deliver packageson a specified street (e.g., Main Street) in a city and the nextdelivery in the dispatch plan may be designated on another street thatis five miles away in the same city. However, there may be otherdesignated deliveries in the dispatch plan on a street (e.g., BroadStreet) in another city that is one mile away from the specified street(e.g., Main Street). As such, a need may exist for improved deliverysystems.

BRIEF SUMMARY

A method, apparatus and computer program product are therefore providedfor generating one or more logistics zones. The exemplary embodimentsmay utilize the logistics zones to determine an optional travel routefor delivery or pickup of packages in the logistics zones. In addition,the exemplary embodiments may determine the planned travel miles for theroute, the planned travel time for the route as well as other suitableshipping data.

Exemplary embodiments implementing logistics zones from a dispatchperspective simplify and improve usability of a dispatch application bybeing able to group planned time together into logical groups calledlogistics zones, based on deliveries and pickups, miles etc. associatedwith a geographic area. For example, in an application interface theselogistics zones may appear as geofenced areas to a user and the user mayselect a logistic zone(s) and assign the selected logistics zone to adriver by dragging and dropping the logistic zone onto data indicating aroute or data indicating a driver.

The exemplary embodiments may aggregate characteristics defined within ageography of a logistics zone. For instance, the aggregatedcharacteristics defined within the geography may correspond toaddresses, homes, buildings, people living in a logistic zone(s),associated income, census types of information, standard industrialclassification (SIC) codes associated with a logistic zone, and anyother suitable characteristics.

The exemplary embodiments may generate planning attributes to deliver aparcel to a house(s)/building(s) in a logistics zone which may includebut is not limited to miles, time, package and/or shipment attributes.These attributes may be used to aggregate information common to thelogistics zone.

The logistics zones may be grouped together to form a larger zone(s) orgeo-fenced area(s). As such, the exemplary embodiments may groupinformation together to enhance the dispatch process. Each logisticszone may be assigned a unique identifier (id).

By utilizing exemplary embodiments, shipments, deliveries, and/orpickups may be aggregated from various sources, shippers, etc. toprovide a limited number of transportation vehicles for travel to anarea of a logistics zone. Packages may be containerized for a particularlogistics zone.

The exemplary embodiments may generate a unique human readable handlinginstruction code assigned to each logistics zone. As logistics zones aregrouped together each logistics zone may be assigned a particularsequence that provides information regarding an order in which packagesof a logistics zone are to be delivered and/or picked up. Additionally,the exemplary embodiments may order each address or building inside of alogistics zone(s). Additionally, one or more priorities may be ascribedto a particular logistics zone(s).

In one example embodiment, a method for generating one or more logisticszones is provided. The method may include generating one or morelogistics zones in response to receipt of an indication of a selectionof a geographic area. The logistics zones may be generated based in parton items of street segment attribute data. Each of the logistics zonesmay include a geo-fenced right zone on a right side of correspondingstreet segments and a geo-fenced left zone on a left side of thecorresponding street segments. The method may further includedetermining addresses in each of the logistics zones based in part onanalyzing the items of street segment attribute data. The method mayfurther include generating a travel route for delivery or pickup ofpackages within the logistics zones based in part on a determined traceorder of the logistics zones specifying a sequential order in which totravel within the logistics zones in response to determining a shortesttravel path.

In another example embodiment, an apparatus for generating one or morelogistics zones is provided. The apparatus may include a processor and amemory including computer program code. The memory and computer programcode are configured to, with the at least one processor, cause theapparatus to at least perform operations including generating one ormore logistics zones in response to receipt of an indication of aselection of a geographic area. The logistics zones may be generatedbased in part on items of street segment attribute data. Each of thelogistics zones may include a geo-fenced right zone on a right side ofcorresponding street segments and a geo-fenced left zone on a left sideof the corresponding street segments. The memory and computer programcode are also configured to, with the processor, cause the apparatus todetermine addresses in each of the logistics zones based in part onanalyzing the items of street segment attribute data. The memory andcomputer program code are also configured to, with the processor, causethe apparatus to generate a travel route for delivery or pickup ofpackages within the logistics zones based in part on a determined traceorder of the logistics zones specifying a sequential order in which totravel within the logistics zones in response to determining a shortesttravel path.

In yet another example embodiment, a computer program product forgenerating one or more logistics zones is provided. The computer programproduct includes at least one computer-readable storage medium havingcomputer-executable program code instructions stored therein. Thecomputer-executable program code instructions may include program codeinstructions configured to generate one or more logistics zones inresponse to receipt of an indication of a selection of a geographicarea. The logistics zones may be generated based in part on items ofstreet segment attribute data. Each of the logistics zones may include ageo-fenced right zone on a right side of corresponding street segmentsand a geo-fenced left zone on a left side of the corresponding streetsegments. The computer program product may further include program codeinstructions configured to determine addresses in each of the logisticszones based in part on analyzing the items of street segment attributedata. The computer program product may further include program codeinstructions configured to generate a travel route for delivery orpickup of packages within the logistics zones based in part on adetermined trace order of the logistics zones specifying a sequentialorder in which to travel within the logistics zones in response todetermining a shortest travel path.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 is an overview of a system that can be used to practiceembodiments of the invention;

FIG. 2 is a schematic diagram of a carrier system according to anexemplary embodiment of the invention;

FIG. 3 is a schematic block diagram of a mobile device in accordancewith an exemplary embodiment of the invention;

FIG. 4 is a diagram illustrating a user interface indicating a selectionof a geographic area according to an exemplary embodiment of theinvention;

FIG. 5A is a diagram illustrating a street segment according to anexemplary embodiment of the invention;

FIG. 5B is a diagram illustrating a node connecting street segmentsaccording to an exemplary embodiment of the invention;

FIGS. 6-12 are diagrams illustrating user interfaces according toexemplary embodiments of the invention;

FIG. 13 is a diagram illustrating street segments according to anexemplary embodiment;

FIG. 14 is a diagram illustrating logistics zones according to anexemplary embodiment;

FIG. 15 is a diagram illustrating a trace order of logistics zonesaccording to an exemplary embodiment; and

FIG. 16 is a flowchart illustrating operations and processes that may beused in accordance with various embodiments of the invention.

DETAILED DESCRIPTION

Various embodiments of the present invention now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the inventions are shown. Indeed, theseinventions may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” is used herein in both the alternativeand conjunctive sense, unless otherwise indicated. The terms“illustrative” and “exemplary” are used to be examples with noindication of quality level. Like numbers refer to like elementsthroughout.

As defined herein a “computer-readable storage medium,” which refers toa non-transitory, physical or tangible storage medium (e.g., volatile ornon-volatile memory device), may be differentiated from a“computer-readable transmission medium,” which refers to anelectromagnetic signal.

Various embodiments provide systems, methods and computer programproducts that facilitate improved dispatching of resources. In someembodiments, digital maps are analyzed to create road segments withnodes between the segments. Data relating to the segments are alsostored in relation to the segments (e.g., addresses,commercial/residential status, etc.) A user may select a geographic areaand the system may identify the segments within the selected area. Withthese segments identified, the system can then identify zones related tothe segments (e.g., addresses on the left or right side of a segment,all addresses associated with one or more segments, etc.) and link theassociated data with the zones. When dispatching resources, the systemmay assign zones to the resources and create a suggested sequence forservicing the zones (e.g., a trace route). Work measurements within thezones may also be generated and evaluated such that the workload betweenthe different resources may be balanced. The resources may be personnel,any type of delivery vehicle (e.g., goods, parcels, stocking, taxis,buses) or service vehicle (e.g., refuse collection, meter reader, etc.).

I Exemplary System Architecture

The system may include one or more mobile assets 100, one or morecarrier systems 110, one or more Global Positioning System (GPS)satellites 115, one or more networks 135, one or more radio frequencyidentification (RFID) readers/interrogators 140, one or more mobiledevices 150, and/or the like as illustrated in FIG. 1 . Each of thesecomponents, entities, devices, systems, and similar words used hereininterchangeably may be in direct or indirect communication with, forexample, one another over the same or different wired or wirelessnetworks. Additionally, while FIG. 1 illustrates the various systementities as separate, standalone entities, the various embodiments arenot limited to this particular architecture.

A Exemplary Mobile Asset

In various embodiments, a mobile asset 100 may be a tractor, truck,vehicle, a trailer, a tractor and trailer combination, a van, a flatbedtruck, a delivery vehicle, and/or the like. In one embodiment, eachmobile asset 100 may be associated with a unique mobile asset identifier(such as a mobile asset ID) that uniquely identifies the mobile asset100. The mobile asset 100 may be mobile in the sense that it may be ableto move from one location to another under its own power. The uniquemobile asset ID (e.g., trailer ID, tractor ID, vehicle ID, and/or thelike) may include characters, such as numbers, letters, symbols, and/orthe like. For example, an alphanumeric mobile asset ID (e.g.,“1221A445533AS445”) may be associated with each mobile asset 100. Inanother embodiment, the unique mobile asset ID may be the license plate,registration number, or other identifying information assigned to themobile asset 100. FIG. 1 represents an embodiment in which the mobileasset 100 is a tractor, a trailer, or a tractor and trailer combination.

FIG. 1 shows one or more computing entities, devices, and/or similarwords used herein interchangeably that are associated with the mobileasset 100, such as an information/data collection device 130 or othercomputing entities. The data collection device 130 that may be attached,affixed, disposed upon, integrated into, or part of a mobile asset 100.The information/data collection device 130 may collect location andtelematics information/data and transmit/send the information/data tothe mobile device 150, and/or the carrier system 110 via one of severalcommunication methods.

In one embodiment, each mobile asset 100 may have an RFID tag/sensorattached or affixed thereto that stores the corresponding mobile assetID (e.g., trailer ID, tractor ID, vehicle ID, and/or the like). Such anRFID tag/sensor can be placed inside a mobile asset 100, or affixed toan outer surface of a mobile asset 100, for example. The RFIDtags/sensors may be passive RFID tags/sensors, active RFID tags/sensors,semi-active RFID tags/sensors, battery-assisted passive RFIDtags/sensors, and/or the like. Thus, the RFID tags/sensors can includesome or all of the following components: one or more input interfacesfor receiving information/data, one or more output interfaces fortransmitting information/data, a processor, a clock, memory modules, anda power source.

In another embodiment, each mobile asset 100 may have its correspondingmobile asset ID (e.g., trailer ID, tractor ID, vehicle ID, and/or thelike) visible on the exterior of the mobile asset 100. For example, thelicense plate number, registration number, alphanumeric characters, orother identifying information may be on the exterior of the mobile assetsuch that it can be capture (e.g., trailer ID, tractor ID, vehicle ID,and/or the like) and properly identify it via analysis.

B Exemplary Carrier System

FIG. 2 provides a schematic of a carrier system 110 according to oneembodiment of the present invention. In general, the term “system” mayrefer to, for example, one or more computers, computing devices,computing entities, mobile phones, desktops, tablets, notebooks,laptops, distributed systems, servers, blades, gateways, switches,processing devices, processing entities, relays, routers, network accesspoints, base stations, the like, and/or any combination of devices orentities adapted to perform the functions, operations, and/or processesdescribed herein. Such functions, operations, and/or processes mayinclude, for example, transmitting, receiving, operating on, processing,displaying, storing, determining, creating/generating, monitoring,evaluating, comparing, and/or similar terms used herein interchangeably.In one embodiment, these functions, operations, and/or processes can beperformed on data, content, information, and/or similar terms usedherein interchangeably.

As indicated, in one embodiment, the carrier system 110 may also includeone or more communications interfaces 320 for communicating with variouscomputing entities, such as by communicating data, content, information,and/or similar terms used herein interchangeably that can betransmitted, received, operated on, processed, displayed (e.g., viadisplay 380), stored, and/or the like. For instance, the carrier system110 may communicate with mobile assets 100, RFID interrogators/readers140, mobile devices 150, and/or the like.

As shown in FIG. 2 , in one embodiment, the carrier system 110 mayinclude or be in communication with one or more processing elements 305(also referred to as processors, processing circuitry, and/or similarterms used herein interchangeably) that communicate with other elementswithin the carrier system 110 via a bus, for example. As will beunderstood, the processing element 305 may be embodied in a number ofdifferent ways. For example, the processing element 305 may be embodiedas one or more complex programmable logic devices (CPLDs),microprocessors, multi-core processors, coprocessing entities,application-specific instruction-set processors (ASIPs), and/orcontrollers. Further, the processing element 305 may be embodied as oneor more other processing devices or circuitry. The term circuitry mayrefer to an entirely hardware embodiment or a combination of hardwareand computer program products. Thus, the processing element 305 may beembodied as integrated circuits, application specific integratedcircuits (ASICs), field programmable gate arrays (FPGAs), programmablelogic arrays (PLAs), hardware accelerators, other circuitry, and/or thelike. As will therefore be understood, the processing element 305 may beconfigured for a particular use or configured to execute instructionsstored in volatile or non-volatile media or otherwise accessible to theprocessing element 305. As such, whether configured by hardware orcomputer program products, or by a combination thereof, the processingelement 305 may be capable of performing steps or operations accordingto embodiments of the present invention when configured accordingly.

In one embodiment, the carrier system 110 may further include or be incommunication with non-volatile memory 310 (also referred to asnon-volatile storage, memory, memory storage, memory circuitry and/orsimilar terms used herein interchangeably). In one embodiment, thenon-volatile storage or memory may include one or more non-volatilestorage or memory media as described above, such as hard disks, ROM,PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks,CBRAM, PRAM, FeRAM, RRAM, SONOS, racetrack memory, and/or the like. Aswill be recognized, the non-volatile storage or memory media may storedatabases, database instances, database carrier systems,information/data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like. The termdatabase, database instance, database carrier system, and/or similarterms used herein interchangeably may refer to a structured collectionof records or information/data that is stored in a computer-readablestorage medium, such as via a relational database, hierarchicaldatabase, and/or network database.

In one embodiment, the carrier system 110 may further include or be incommunication with volatile memory 315 (also referred to as volatilestorage, memory, memory storage, memory circuitry and/or similar termsused herein interchangeably). In one embodiment, the volatile memory 315may also include one or more volatile storage or memory media asdescribed above, such as RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDRSDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM, VRAM, cachememory, register memory, and/or the like. As will be recognized, thevolatile storage or memory media may be used to store at least portionsof the databases, database instances, database carrier systems,information/data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like being executedby, for example, the processing element 305. Thus, the databases,database instances, database carrier systems, information/data,applications, programs, program modules, scripts, source code, objectcode, byte code, compiled code, interpreted code, machine code,executable instructions, and/or the like may be used to control certainaspects of the operation of the carrier system 110 with the assistanceof the processing element 305 and operating system.

As indicated, in one embodiment, the carrier system 110 may also includeone or more communications interfaces 320 for communicating with variouscomputing entities, such as by communicating information/data, content,information, and/or similar terms used herein interchangeably that canbe transmitted, received, operated on, processed, displayed, stored,and/or the like. For instance, the carrier system 110 may communicatewith computing entities or communication interfaces of the mobile asset100 (e.g., tractor, trailer, tractor and/or trailer, delivery vehicle),RFID interrogators/readers 140, mobile devices 150, and/or the like.

Such communication may be executed using a wired information/datatransmission protocol, such as fiber distributed information/datainterface (FDDI), digital subscriber line (DSL), Ethernet, asynchronoustransfer mode (ATM), frame relay, information/data over cable serviceinterface specification (DOCSIS), or any other wired transmissionprotocol. Similarly, the carrier system 110 may be configured tocommunicate via wireless external communication networks using any of avariety of protocols, such as GPRS, UMTS, CDMA2000, 1xRTT, WCDMA,TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IRprotocols, Bluetooth protocols, USB protocols, and/or any other wirelessprotocol. Although not shown, the carrier system 110 may include or bein communication with one or more input elements, such as a keyboardinput, a mouse input, a touch screen/display input, audio input,pointing device input, joystick input, keypad input, and/or the like.The carrier system 110 may also include or be in communication with oneor more output elements (not shown), such as audio output, video output,screen/display output, motion output, movement output, and/or the like.

In addition to the communication interface(s), the interface(s) may alsoinclude at least one user interface that may include one or moreearphones and/or speakers, a display 380, and/or a user input interface382. The user input interface, in turn, may comprise any of a number ofdevices allowing the carrier system to receive data from a user, such asa microphone, a keypad, keyboard, a touch display, a joystick, imagecapture device, pointing device (e.g., mouse), stylus or other inputdevice.

As will be appreciated, one or more of the carrier system's 110components may be located remotely from other carrier system 110components, such as in a distributed system. Furthermore, one or more ofthe components may be combined and additional components performingfunctions described herein may be included in the carrier system 110.Thus, the carrier system 110 may be adapted to accommodate a variety ofneeds and circumstances.

In an exemplary embodiment, the processing element 305 may be incommunication with and may otherwise control a logistics zone module378. The logistics zone module 378 may be any means such as a device orcircuitry operating in accordance with software or otherwise embodied inhardware or a combination of hardware and software thereby configuringthe device or circuitry (e.g., a processor, controller, microprocessoror the like) to perform the corresponding functions of the logisticszone module 378, as described below. In examples in which software isemployed, a device or circuitry (e.g., processing element 305 in oneexample) executing the software forms the structure associated with suchmeans. As such, for example, the logistics zone module 378 may beconfigured to, among other things, facilitate generation of one or morelogistics zones for delivery or pickup of one or more packages, asdescribed more fully below.

C Exemplary Mobile Device

FIG. 3 provides an illustrative schematic representative of a mobiledevice 150 (e.g., in-mobile-asset device, FDT2 device) that can be usedin conjunction with embodiments of the present invention. Mobile devices150 can be operated by various parties, including operators of mobileassets 100. As shown in FIG. 3 , a mobile device 150 (e.g.,in-mobile-asset device, FDT2 device, etc.) can include an antenna 412, atransmitter 404 (e.g., radio), a receiver 406 (e.g., radio), and aprocessing element 408 that provides signals to and receives signalsfrom the transmitter 404 and receiver 406, respectively.

The signals provided to and received from the transmitter 404 and thereceiver 406, respectively, may include signaling information/data inaccordance with an air interface standard of applicable wireless systemsto communicate with various entities, such as mobile assets 100, carriersystem 110, RFID interrogators/readers 140, and/or the like. In thisregard, the mobile device 150 (e.g., in-mobile-asset device, FDT2device, etc.) may be capable of operating with one or more air interfacestandards, communication protocols, modulation types, and access types.More particularly, the mobile device 150 (e.g., in-mobile-asset device,FDT2 device, etc.) may operate in accordance with any of a number ofwireless communication standards and protocols. In a particularembodiment, the mobile device 150 (e.g., in-mobile-asset device, FDT2device, etc.) may operate in accordance with multiple wirelesscommunication standards and protocols, such as GPRS, UMTS, CDMA2000,1xRTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX,UWB, IR protocols, Bluetooth protocols, USB protocols, and/or any otherwireless protocol.

According to one embodiment, the mobile device 150 (e.g.,in-mobile-asset device, FDT2 device, etc.) may include a locationdetermining device and/or functionality. For example, the mobile device150 (e.g., in-mobile-asset device, FDT2 device, etc.) may include a GPSmodule adapted to acquire, for example, latitude, longitude, altitude,geocode, course, and/or speed data. In one embodiment, the GPS moduleacquires information/data, sometimes known as ephemerisinformation/data, by identifying the number of satellites in view andthe relative positions of those satellites.

The mobile device 150 (e.g., in-mobile-asset device, FDT2 device, etc.)may also comprise a user interface (that may include a display 416coupled to a processing element 408) and/or a user input interface(coupled to a processing element 408). The user input interface cancomprise any of a number of devices allowing the mobile device 150(e.g., in-mobile-asset device, FDT2 device, etc.) to receiveinformation/data, such as a keypad 418 (e.g., hard or soft), a touchdisplay, voice or motion interfaces, a barcode reader, a RFID tagreader, and/or other input device. In embodiments including a keypad418, the keypad 418 can include (or cause display of) the conventionalnumeric (0-9) and related keys (#, *), and other keys used for operatingthe mobile device 150 (e.g., in-mobile-asset device, FDT2 device, etc.)and may include a full set of alphabetic keys or set of keys that may beactivated to provide a full set of alphanumeric keys. In addition toproviding input, the user input interface can be used, for example, toactivate or deactivate certain functions, such as screen savers and/orsleep modes.

The mobile device 150 (e.g., in-mobile-asset device, FDT2 device, etc.)can also include volatile storage or memory 422 and/or non-volatilestorage or memory 424, which can be embedded and/or may be removable.For example, the non-volatile memory may be ROM, PROM, EPROM, EEPROM,flash memory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM, FeRAM,RRAM, SONOS, racetrack memory, and/or the like. The volatile memory maybe RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM,DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM, VRAM, cache memory, registermemory, and/or the like. The volatile and non-volatile storage or memorycan store databases, database instances, database carrier systems,information/data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like to implement thefunctions of the mobile device 150 (e.g., in-mobile-asset device, FDT2device, etc.).

II Exemplary System Operation

Reference will now be made to example embodiments of a system forgenerating one or more logistics zones. The logistics zones andassociated data (e.g., street segment attribute data) may be utilized inpart to perform shipping tasks such as, for example, generating shippingroutes, routing plans, dispatch plans, handling instructions and othersuitable tasks, as described more fully below.

A Generating Logistics Zones

Referring now to FIG. 4 , a diagram illustrating a zone of interest isprovided according to an exemplary embodiment. In the example embodimentof FIG. 4 , the logistics zone module 378 may receive input of aselection of a zone of interest 3 and may increase/expand the visibleindicia denoting the zone of interest in a pop-up window 5. Theselection of the areas of interest may be received via a user inputinterface (e.g., user input interface 382) in response to a userselecting the zone of interest 3. The logistics zone module 378 maygenerate one or more logistic zones based in part on one or more streetsegment attributes and/or definitions, as described more fully below.

Referring now to FIGS. 5A and 5B, diagrams illustrating street segmentsand a node connecting street segments are provided according to anexemplary embodiment. The logistics zones of the exemplary embodimentsmay be generated based in part on street segment attributes and/ordefinitions and in this regard the logistics zones may define one ormore geographies that include addresses, as described more fully below.

In the example embodiment of FIG. 5A, the logistics zone module 378 maygenerate a street segment 7 having multiple points (e.g., six points).In some example embodiments, a street segment may include two points(e.g., a From Point and To Point). The logistics zone module 378 maygenerate the street segment 7 in response to receipt of an indication ofa selection of a street(s) (e.g., from a digital map). The logisticszone module 378 may determine the longitude and latitude coordinates ofthe points of a street segment (e.g., street segment 7).

In an example embodiment, the logistics zone module 378 may definestreet segment attributes and/or definitions for a street segment(s)(e.g., street segment 7) including, but not limited to: (1) City—CityRight (e.g., a city on the right side of the segment (e.g., Atlanta,GA)), City Left (e.g., a city on the left side of the segment) (e.g.,Norcross, GA) (e.g., in some instances the city on the right of thesegment and the left of the segment may be the same city); (2)Classification—Interstate, Local Road, Highway, Primary Road, etc.; (3)Country Country Left, Country Right; (4) Default Name (e.g., PeachtreeStreet, etc.); (5) Direction One way, Two way, etc.; (6)Distance—Distance of the segment (e.g., street segment 7) inmiles/kilometers (e.g., distance between each segment, distance betweenFrom Point and To Point, etc.); (7) Elevation—To Elevation (e.g., the ToPoint is on a flat road), From Elevation (e.g., the From Point is on aRamp); (8) From Point (e.g., starting longitude and latitude point), ToPoint (e.g., ending longitude and latitude point); (9) Identification(ID)—Unique ID number; (10) High Address Number—High Address Right(e.g., the high address on the right side of the segment), High AddressLeft (e.g., the high address on the left side of the segment); (11) LowAddress Number—Low Address Right (e.g., low address on the right side ofthe segment), Low Address Left (e.g., low address on the left side ofthe segment); (12) Points—Longitude and Latitude points (e.g.,coordinates) in order (e.g., From Point To Point) that determine asegment (e.g., street segment 7); Postal Code—Postal Code Right, PostalCode Left; (13) Street Prefix—Street Prefix Right, Street Prefix Left(e.g., N, S, E, W, etc.); (14) Street Suffix—Street Suffix Right, StreetSuffix Left (e.g., W, NE, SE, NW, etc.); (15) Street Type—Road (RD),Avenue (AVE), Drive (DR), Boulevard (BLVD), etc.; (16) Time—Time totravel the street segment (e.g., street segment 7); (17) Weight Maximumweight allowed (e.g., for a given street corresponding to a streetsegment) in pounds (lbs.) or kilograms; or (18) any other suitablestreet segment attributes and/or definitions data (e.g., location data(e.g., longitude and latitude coordinates) of doors of houses and/orbuildings along a street segment(s)). The defined street segmentattributes and/or definitions for the street segments may be stored in amemory (e.g., non-volatile memory 310, volatile memory 315).

As shown in FIG. 5B, a node (e.g., node 9 (e.g., an intersection)) mayconnect segments (e.g., segment 2, segment 4). The nodes may beassociated with information indicating the segments that connect withthe respective nodes. The logistics zone module 378 may generatelogistics zones based in part on the street segment attributes and/ordefinitions associated with segments and nodes. Additionally, thelogistics zone module 378 may determine a travel path (e.g., a deliveryroute) based in part on evaluating the distance between one or morenodes.

Referring now to FIG. 6 , a diagram illustrating a user interface forselecting a geographic area including street segments and nodes isprovided according to an exemplary embodiment. In the example embodimentof FIG. 6 , the logistics zone module 378 may define a geo-fence 10(also referred to herein as geo-fence area 10) on a map of the userinterface 11 in response to receipt of input of a selection of ageographic area. The receipt of the input of the selection of thegeographic area may be in response to receipt of a selection by a uservia the user input interface (e.g., user input interface 382). Forinstance, in some example embodiments, the user may utilize a pointer ofthe user input interface (e.g., user input interface 382) to draw acircle or lasso around a geographic area of interest to trigger thelogistics zone module 378 to generate a geo-fence (e.g., geo-fence 10).In response to selecting the geographic area, the logistics zone module378 may identify and trace the corresponding street segments of thegeo-fence 10. In addition, the logistics zone module 378 may determinethe nodes of the geo-fence 10 and may indicate the nodes on thegeo-fence 10. The nodes may occur at intersections (e.g., node 14) andendpoints (e.g., node 26) of the street segments. The logistics zonemodule 378 may also include items of visible indicia 12 identifying thestreet segments.

Referring now to FIG. 7 , a diagram illustrating a user interface forgenerating offset points of street segments is provided according to anexemplary embodiment. In the example embodiment of FIG. 7 , thelogistics zone module 378 may generate the user interface 14 in responseto receipt of an indication 6 of an offset distance (e.g., 200 feet)from each of the segments (e.g., From point 21—To Point 22, From Point3—To Point 4, etc.) in which to generate a logistics zone.

The logistics zone module 378 may also determine the longitude andlatitude coordinates of the offset points (e.g., offset point 15) andmay include items of visible indicia 8 in the user interface 14specifying the longitude and latitude coordinates.

Referring now to FIG. 8 , a diagram illustrating a user interfaceindicating the nodes of a geo-fence is provided according to anexemplary embodiment. In the example embodiment of FIG. 8 , thelogistics zone module 378 determined that there were thirteen nodes inthe geo-fence 18 (e.g., geo-fence 10). In this regard, the logisticszone module 378 included visible indicia 20 indicating the nodes of thegeo-fence 18 in the user interface 19. The logistics zone module 378 maydetermine the nodes of the geo-fence 18 in response to receipt of anindication of a selection of a node test tab 21.

Referring now to FIG. 9 , a diagram illustrating a user interface fordetermining node headings is provided according to an exemplaryembodiment. In the exemplary embodiment of FIG. 9 , the logistics zonemodule 378 may generate the user interface 22 in response to a receiptof an indication of a selection of the Id node arcs tab 23. Thelogistics zone module 378 may determine the node headings (e.g.,direction (e.g., North)) of a geo-fence (e.g., geo-fence 24) based inpart on the longitude and latitude coordinates of the nodes. Thelogistics zone module 378 may include visible indicia 25 indicating thelongitude and latitude coordinates of the nodes in the user interface22. For purposes of illustration and not of limitation, the logisticszone module 378 determined that the node heading for Node 1 Arc FromPoint 1 is a North (N) direction.

Referring now to FIG. 10 , a diagram illustrating a user interface forselecting a street segment(s) is provided according to an exemplaryembodiment. In the exemplary embodiment of FIG. 10 , the logistics zonemodule 378 may generate the user interface 26 in response to a receiptof an indication of a selection of the select street tab 27. Thelogistics zone module 378 may indicate a selection of a streetsegment(s) (e.g., street segment 29) of a geo-fence (e.g., geo-fence 28)in response to receipt of an indication that the street segment (e.g.,street segment 29) was chosen. In the example embodiment of FIG. 10 ,the logistics module 378 may include visible indicating the points alongthe selected street segment 29 and may include visible indicia 30 in theuser interface 26 indicating the number (e.g., 9) of points on theselected segment 29.

Referring now to FIG. 11 , a diagram illustrating a user interface forgenerating logistics zones is provided according to an exemplaryembodiment. In the example embodiment of FIG. 11 , the logistics zonemodule 378 may generate the user interface 17 in response to creatingthe offset points from each of the segments of a selected geographicarea. The logistics zone module 378 may generate one or more logisticszones (e.g., logistics zone 16, logistics zone 41) based in part onconnecting the offset points. The logistics zone 16 may be a geo-fencedzone on a left side of a street and the logistics zone 18 may be ageo-fenced zone on a right side of the street. The logistics zones(e.g., logistics zone 16, logistics zone 41), generated by the logisticszone module 378, may include all addresses in the geo-fenced area of therespective logistics zones. The logistics zone module 378 may determinethe addresses for the logistics zones based in part on analyzing theaddress information associated with the street segment attributes and/ordefinition data.

In one example embodiment, in response to receipt of an indication of alasso or a circle around a geographic area that includes street segmentsof the area, the logistics zone module 378 may automatically create a(e.g., geo-fence 10), and the logistics zones (e.g., logistics zone 16,logistic zone 41) of the geo-fence.

Referring now to FIG. 12 , a diagram illustrating logistics zones isprovided according to an exemplary embodiment. In the example embodimentof FIG. 12 , the logistics zone module 378 may generate right and leftlogistics zones of each of the street segments for a geo-fence (e.g.,geo-fence 10) area in a user interface 31. The right and left logisticszones of each of the street segments may be generated based in part onoffset points from each of the street segments, in the manner describedabove. The logistics zone module 378 may determine the addresses foreach of the logistics zones based in part on analyzing the addressinformation associated with the street segment attributes and/ordefinition data.

Referring now to FIG. 13 , a diagram illustrating street segmentsutilized in part to generate one or more logistics zones is provided. Inthe example embodiment of FIG. 13 , the logistics zone module 378 mayanalyze the street segments such as 1st street, 2nd street, A-Avenue andB-Avenue to define logistics zones. The street segments such as 1ststreet, 2nd street, A-Avenue and B-Avenue include segments (e.g.,segments 51, 53) and nodes (e.g., nodes 43, 45, 47, 49) and areassociated with street segment attributes and/or definitions data. Inthe example embodiment of FIG. 13 , the logistics zones module 378 maygenerate an offset distance (e.g., 200 feet) from the respective streetsegments (e.g., 1st street, 2nd street, A-Avenue and B-Avenue) togenerate one or more logistics zones as described more fully below withrespect to FIG. 14 .

Referring now to FIG. 14 , a diagram illustrating one or more logisticszones is provided. In the example embodiment of FIG. 14 , the logisticszone module 378 may generate logistics zones that are offset a distance(e.g., 200 feet) from street segments (e.g., 1st street, 2nd street,A-Avenue and B-Avenue). For instance, in the example embodiment of FIG.5 , the logistics zone module 378 may generate logistics zones 55, 57,59, 61, 63, 65, 67, 69, 71, 73, 75, 77, 79, 81, 83, 85, 87, 89, 91, 93,95, 97, 99, 101 and 103 that may be offset from a distance (e.g., 200feet) from respective street segments. The logistics zone module 378 maydetermine the addresses for each of the logistics zones based in part onanalyzing address information associated with the street segmentattributes and/or definition data.

The logistics zone module 378 may generate one or more unique handlinginstructions (e.g., human readable handling instructions) and codes forone or more of the logistics zones. The handling instructions mayinclude data specifying packages for delivery and/or pickup at addressesin corresponding logistics zones.

In some example embodiments, the logistics zone module 378 mayfacilitate grouping of logistics zones (e.g., logistics zones 61, 63, 65and 67) together to form larger logistics zones or geo-fenced areas. Inthis manner, the logistics zone module 378 may group informationtogether to enhance a dispatch process. For instance, the logistics zonemodule 378 may generate a dispatch plan for the larger group oflogistics zones in response to receipt of an indication of a selectionof the group of logistics zones. As logistics zones are grouped togetherby the logistics zone module 378, the logistics zone module 378 mayassign a particular sequence that provides information regarding theorder in which logistics zones of the group of logistics zones areassigned for delivery or pickup of packages. Additionally, the logisticszone module 378 may generate an order for delivery or pickup of packagesfor each address or building inside a logistics zone of the group oflogistics zones. The logistics zone module 378 may also assign one ormore priorities to a particular logistics zone(s). The priorities may bebased on delivery times for packages within the zones or other reasons.

B Utilizing Logistics Zones in Part to Generate Routes, Instructions &Determine Other Data

Referring now to FIG. 15 , a diagram illustrating a trace ordering isprovided according to an exemplary embodiment. In the example embodimentof FIG. 15 , the logistics zone module 378 may generate a trace orderingfor the generated logistics zones in the user interface 32. The traceordering generated by the logistics zone module 378 may be determinedbased in part on the logistics zones module calculating the shortesttravel path in the generated logistics zones (e.g., between zones,within zones, etc.). The logistics zone module 378 may determine theshortest travel path based in part on utilizing the informationindicating the distance of the street segments and the time to travelthe street segments that is associated with the street segmentattributes and/or definitions data. In the example embodiment of FIG. 15, the logistics zone module 378 determined a trace order of 1 through 26traces for the logistics zones.

In one example embodiment, the trace order generated by the logisticszone module 378 may be designated as travel route for a vehicle (e.g.,mobile asset 100) to deliver or pickup packages in the logistics zones.As such, in this example embodiment, the logistics zone module 378 maygenerate routing instructions based on the trace order (e.g., traceorder 1-26) which may instruct a driver of the vehicle (e.g., mobileasset 100) to deliver or pickup packages in the geographic area (e.g.,geo-fence 10) of the logistics zones according to the trace order. Thelogistics zone module 378 may send the routing instructions to a mobiledevice (e.g., mobile device 150) of the driver of the vehicle. In thismanner, the mobile device (e.g., mobile device 150) may show (e.g., viadisplay 416) the routing instructions to the driver during travel of theroute.

In another example embodiment, the logistics zone module 378 maydetermine a trace order for a subset of the logistics zones of the userinterface 32 in response to receipt of an indication of a selection ofthe subset. For purposes of illustration and not of limitation, inresponse to receipt of an indication of a selection of logistics zones33, 34, 35, 36 and 37, the logistics zone module 378 may determine atrace order of 1, 2, 9, 10 and 13 for a travel route for delivery orpickup of packages. In this regard, the logistics zone module 378 maygenerate routing instructions based on this trace order (e.g., traceorder 1, 2, 9, 10 and 13) which may be sent to a mobile device (e.g.,mobile device 150) of a driver and as such the driver may travel along apath starting from trace 1 to trace 2, trace 9, trace 10 and trace 13.As such, for delivery or pickup of packages in logistics zones 33, 34,35, 36, and 37, the driver may utilize the vehicle (e.g., mobile asset100) to travel along the route per the defined trace order (e.g., traceorder 1, 2, 9, 10 and 13).

In an instance in which addresses remain the same (e.g., new houses arenot built in the area) for a geographic area (e.g., geo-fence 10), thelogistics zone module 378 may reuse the trace order (e.g., trace order1-26) for subsequent travel along the route without regenerating thetrace order. On the other hand, in an instance in which the logisticszone module 378 detects that one or more addresses of the geographicarea (e.g., geo-fence 10) has changed since a previously generated traceorder, the logistics zone module 378 may regenerate a trace order androute for the geographic area.

The logistics zone module 378 may determine the planned travel miles fora route based in part on the trace order of the logistics zones. Forinstance, the logistics zone module 378 may analyze the distances ofeach of the street segments of the trace order (e.g., trace order 1-26)based in part on analyzing the street segment attributes and/ordefinition data and may determine the total planned miles for the routeby adding the distances of each of the street segments corresponding tothe logistics zones of the trace order of the route. In addition,logistics zone module 378 may determine the planned travel time for aroute based in part on analyzing the time to travel of each of thestreet segments in the street segment attributes and/or definition data.In this regard, the logistics zone module 378 may determine the totaltravel time for a route by adding the times of each of the streetsegments corresponding to the logistics zones of the trace order of theroute.

The logistics zones module 378 may generate one or more dispatch plansbased in part on the logistics zones and a trace order for a travelroute (e.g., delivery route). For example, the logistics zones module378 may utilize the data associated with the logistics zones to generateand schedule one or more dispatch plans that directs the sequence inwhich to pickup and/or to deliver packages in a designated geographicalarea (e.g., geo-fence area 10). In this regard, for example, thelogistics zones module 378 may generate a dispatch plan for ageographical area for a route (e.g., based on a trace order of logisticszones) for delivery or pickup of packages in one or more logistics zones(e.g., logistics zones 33, 34, 35, 36, and 37). The logistics zonesmodule 378 may include data in the dispatch plan(s) indicating theservice sequence (e.g., delivery sequence) for the addresses of thelogistics zones along the route.

In addition, the logistics zones module 378 may generate one or morehandling instructions based on the logistics zones of a route (e.g.,delivery route). For instance, the handling instructions may begenerated by the logistics zones module 378 to route one or morepackages to a position within a hub facility (e.g., shipping warehouse)for directing the package to a next location along a delivery route.Additionally or alternatively, the handling instructions may begenerated by the logistics zone module 378 to facilitate pre-load of apackage(s) in a vehicle (e.g., mobile asset 100) for delivery to thefinal delivery destination of the package. In this regard, the handlinginstruction(s) may identify a package(s) and a load position in thevehicle (e.g., mobile asset 100) for the package(s). By analyzing dataof the logistics zones associated with a trace order for a deliveryroute, the logistics zones module 378 may determine the position andlocation in which one or more packages for the route (e.g., a deliveryor pickup route) should be placed on a vehicle. For purposes ofillustration and not of limitation, the logistics zone module 378 mayanalyze the data (e.g., a trace order) of the logistics zones anddetermine that packages 1-10 are designated for delivery to zone 33which may be a first stop (e.g., a first delivery stop) along a route(e.g., based on trace order 1, 2, 9, 10 and 13). In this regard, forexample, the logistics zones module 378 may generate a handlinginstruction(s) designating that packages 1-10 are to be placed onshelves of the vehicle (e.g., mobile asset 100 (e.g., a truck)) near anexit door of the vehicle so that the packages (e.g., packages 1-10) maybe easily retrieved since the packages are delivered at the first stopin a logistics zone (e.g., logistics zone 33) of the route (e.g., aroute based on trace order 1, 2, 9, 10 and 13).

In some other example embodiments, the logistics zone module 378 maygenerate a special handling instruction(s) for delivery of one or morepackages in one or more of the logistics zones. For example, thelogistics zone module 378 may receive an indication (e.g., by a user viauser input interface 382) to generate a special handling instruction(s)for one or more logistics zones in response to receipt of a selection ofthe logistics zones (e.g., a user selecting the logistics zones with apointer of the user input interface 382). For purposes of illustrationand not of limitation, the special handling instruction(s) may indicatethat one or more small packages (e.g., packages under a predefinedweight/size) for delivery in one of the selected zones (e.g., logisticszone 37) are designated to be included in a container (e.g., placed inbag, etc.) and delivered from a cart. In this regard, based on thespecial handling instruction, a driver of a vehicle (e.g., mobile asset100) in the selected logistics zone (e.g., logistics zone 37) may removea cart from the vehicle in the selected zone and may deliver the smallpackages for the selected logistics zone using the cart.

In some example embodiments, the dispatch plan(s) generated by thelogistics zone module 378 may include the handling instructions for eachof the packages to be delivered and/or picked up according to thedispatch plan.

In some example embodiments, the street segment attributes and/ordefinitions data associated with each of the street segments may includelocation data (e.g., longitude and latitude coordinates) of the door ofthe houses and/or other buildings corresponding to the addresses along arespective street segment(s). As such, in some example embodiments, thelogistics zone module 378 may determine the work measurement (alsoreferred to herein as work measurement time) for one or more logisticszones (e.g., logistics zones 33, 34 and 35). For example, the logisticszone module 378 may determine the work measurement for one or morelogistics zones based in part on calculating the time it takes a driverof a vehicle to walk from the middle of a street, in which the vehiclemay be located, to a front door of houses and/or buildings along thestreet of the logistics zones for delivery and/or pickup of one or morepackages. In this regard, the logistics zone module 378 may determinethe total work measurement time for logistics zones of a route by addingthe work measurement times for each of the logistics zones of the route(e.g., logistics zones 33, 34 and 35).

In some example embodiments, all or a subset of the selected logisticszones (e.g., logistics zones of the user interface 32) may be selected,dragged and dropped (e.g., via a pointer of the user input interface382) on an indication (e.g., a driver's name) of a driver which mayassign the selected zones to the driver for delivery/pickup of packagesin the respective logistics zones.

Referring now to FIG. 16 , an example embodiment of a flowchart fordetermining one or more logistics zones is provided according to anexample embodiment. At operation 1600, an apparatus (e.g., carriersystem 110) may generate one or more logistics zones in response toreceipt of an indication of a selection of a geographic area (e.g.,geo-fence area 10). The logistics zones may be generated based in parton items of street segment attribute data. Each of the logistics zonesmay include a geo-fenced right zone on a right side of correspondingstreet segments and a geo-fenced left zone on a left side of thecorresponding street segments.

At operation 1605, the apparatus (e.g., carrier system 110) maydetermine addresses in each of the logistics zones based in part onanalyzing the items of street segment attribute data. At operation 1610,the apparatus (carrier system 110) may generate a travel route fordelivery or pickup of packages within the logistics zones based in parton a determined trace order (e.g., trace order 1-26) of the logisticszones specifying a sequential order in which to travel within thelogistics zones in response to determining a shortest travel path.

It should be pointed out that FIG. 16 is a flowchart of a system, methodand computer program product according to an example embodiment of theinvention. It will be understood that each block of the flowchart, andcombinations of blocks in the flowchart, can be implemented by variousmeans, such as hardware, firmware, and/or a computer program productincluding one or more computer program instructions. For example, one ormore of the procedures described above may be embodied by computerprogram instructions. In this regard, in an example embodiment, thecomputer program instructions which embody the procedures describedabove are stored by a memory device (e.g., volatile memory 315,non-volatile memory 310, volatile memory 422, non-volatile memory 424)and executed by a processor (e.g., processing element 305, logisticszone module 378, processing device 408). As will be appreciated, anysuch computer program instructions may be loaded onto a computer orother programmable apparatus (e.g., hardware) to produce a machine, suchthat the instructions which execute on the computer or otherprogrammable apparatus cause the functions specified in the flowchartblocks to be implemented. In one embodiment, the computer programinstructions are stored in a computer-readable memory that can direct acomputer or other programmable apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instructions whichimplement the function(s) specified in the flowchart blocks. Thecomputer program instructions may also be loaded onto a computer orother programmable apparatus to cause a series of operations to beperformed on the computer or other programmable apparatus to produce acomputer-implemented process such that the instructions which execute onthe computer or other programmable apparatus implement the functionsspecified in the flowchart blocks.

Accordingly, blocks of the flowchart support combinations of means forperforming the specified functions. It will also be understood that oneor more blocks of the flowchart, and combinations of blocks in theflowchart, can be implemented by special purpose hardware-based computersystems which perform the specified functions, or combinations ofspecial purpose hardware and computer instructions.

In an example embodiment, an apparatus for performing the method of FIG.16 above may comprise a processor (e.g., processing element 305,logistics zone module 378, processing device 408) configured to performsome or each of the operations (1600-1610) described above. Theprocessor may, for example, be configured to perform the operations(1600 1610) by performing hardware implemented logical functions,executing stored instructions, or executing algorithms for performingeach of the operations. Alternatively, the apparatus may comprise meansfor performing each of the operations described above. In this regard,according to an example embodiment, examples of means for performingoperations (1600-1610) may comprise, for example, the processing element305 (e.g., a processor) (e.g., as means for performing any of theoperations described above), the logistics zone module 378, theprocessing device 408 and/or a device or circuitry for executinginstructions or executing an algorithm for processing information asdescribed above.

III Conclusion

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

What is claimed is:
 1. A method comprising: causing presentation of anelectronic map of a user interface; receiving an indication that a userhas provided a lasso gesture around a geographical area within theelectronic map of the user interface: in response to the receiving ofthe indication, causing generation, at the user interface, of anindicator representing a geofence around the geographical area: based atleast in part on the lasso gesture, automatically causing generation atthe user interface of one or more nodes for presentation within theindicator representing the geofence, wherein no nodes are presented atthe user interface in any area outside of the indicator representing thegeofence, each of the one or more nodes is a visual indicator within theelectronic map indicative of a connection point between one or morestreet segments; generating a plurality of offsets for each of the oneor more street segments based on assigning an offset distance from theone or more street segments; in response to the generation of theplurality of offsets, causing generation, at the user interface andwithin the indicator representing the geofence, of a plurality ofcorresponding offset points that define the plurality of offsets, eachoffset point, of the plurality of offset points, being located outsideof a corresponding portion of the one or more street segments of theuser interface based on the offset distance; based at least in part oncausing a connection, at the user interface, of a portion of theplurality of offset points, automatically causing generation, at theuser interface, of one or more indicators representing one or morelogistics zones, a boundary of the one or more indicators being defined,at the user interface, by the portion of the plurality of offset points,the one or more logistics zones are further generated based at least inpart on items of street segment attribute data associated with the oneor more street segments; based at least in part on the generating of theplurality of offsets, causing generation, at the user interface and inin each of the one or more indicators, a geofenced right zone indicatoron a right side of corresponding street segments and a geofenced leftzone indicator on a left side of the corresponding street segmentswherein the geofenced right zone indicator and the geofenced left zoneindicator are displayed outside of the one or more street segments basedon the generating of the plurality of offsets; and based at least inpart on the generating of the geofenced left zone indicator and thegeofenced right zone indicator, automatically generating, a travel routefor a vehicle to travel for delivery or pickup of one or more itemswithin an area corresponding to the geofenced right zone indicator andthe geofenced left zone indicator.
 2. The method of claim 1, furthercomprising determining planned travel miles of the travel route based inpart on a trace order that specifies a sequential order in which totravel within the area corresponding to the geofenced right zoneindicator and the geofenced left zone indicator.
 3. The method of claim1, further comprising determining planned travel time of the travelroute based in part on calculating time to travel each of the one ormore street segments by adding times of each street segment within thelogistics zones.
 4. The method of claim 1, further comprising:determining geo-coordinates of each of the plurality of offsets fromeach of the one or more street segments; and providing visible dataindicating the geo-coordinates of the plurality of offsets in the userinterface presented with visible indicia of the electronic map displayedvia a display device.
 5. The method of claim 1, wherein prior toconnecting the plurality of offset points the method further comprisesdetermining a latitude coordinate and a longitude coordinate of each ofthe plurality of offset points.
 6. The method of claim 1, furthercomprising generating a dispatch plan based in part on a trace orderindicating a shortest travel path between addresses within the arearepresenting the logistics zones indicators, the dispatch planindicating a service sequence in which to pickup or deliver the packagesto the addresses of an area representing the logistics zones indicators.7. The method of claim 6, further comprising generating one or morehandling instructions based in part on analyzing the trace order, theone or more handling instructions specifying a location in which one ormore of the packages associated with the travel route are assigned forplacement in the vehicle or a position in which the packages aredesignated for placement in a hub facility.
 8. The method of claim 1,further comprising determining a work measurement time for delivery orpickup of packages within the area representing the one or moreindicators based in part on calculating a time to walk from the vehicleto a respective doors of buildings corresponding to the addresses.
 9. Anapparatus comprising at least one processor and at least one memoryincluding computer program code, the at least one memory and thecomputer program code configured to, with the processor, cause theapparatus to at least: automatically generate one or more logisticszones at least partially in response to receipt of an indication of alasso gesture selection, via a user interface, of a geographic areaindicated in visible indicia of an electronic map displayed via adisplay device of the apparatus, the lasso gesture selection beingindicated by an indicator, at the user interface, that surrounds thegeographic area; based at least in part on the lasso gesture selection,automatically causing generation, at the user interface, of one or morenodes for presentation within the indicator, wherein no nodes arepresented at the user interface in any area outside of the indicatoreach of the one or more nodes is a visual indicator within theelectronic map indicative of a connection point between one or morestreet segments; generating a plurality of offsets for each of the oneor more street segments based on assigning an offset distance from theone or more street segments; in response to the generation of theplurality of offsets, causing generation, at the user interface andwithin the indicator, of a plurality of corresponding offset points thatdefine the plurality of offsets, each offset point, of the plurality ofoffset points, being located outside of a corresponding portion of theone or more street segments of the user interface based on the offsetdistance; based at least in part on causing a connection, at the userinterface, of a portion of the plurality of corresponding offset points,automatically causing generation of one or more indicators representingone or more logistics zones, a boundary of the one or more indicatorsbeing defined, at the user interface, by the portion of the plurality ofcorresponding offset points; generate, in each of the one or morelogistics zones of the electronic map of the user interface, a geofencedright zone on a right side of corresponding street segments and ageofenced left zone on a left side of the corresponding street segments;generate a travel route for a vehicle to travel for delivery or pickupof items within at least an area corresponding to the geofenced rightzone and the geofenced left zone based in part on a determined traceorder specifying a sequential order in which to travel within thegeofenced right zone and the geofenced left zone; and drag or drop,within the user interface, each of the one or more logistic zones todata indicating the travel route, the drag or drop being indicative ofassigning a driver to the vehicle for the delivery or pickup of theitems, along the travel route, within the geofenced right zone and thegeofenced left zone.
 10. The apparatus of claim 9, wherein the memoryand computer program code are further configured to, with the processor,cause the apparatus to determine planned travel miles of the travelroute based in part on calculating distances of each of the one or morestreet segments in response to analyzing the items of street segmentattribute data.
 11. The apparatus of claim 9, wherein the memory andcomputer program code are further configured to, with the processor,cause the apparatus to determine planned travel time of the route basedin part on calculating time to travel each of the one or more streetsegments in response to analyzing the items of street segment attributedata.
 12. The apparatus of claim 9, wherein the memory and computerprogram code are further configured to, with the processor, cause theapparatus to: determine geo-coordinates of each of the plurality ofoffsets from each street segment of the one or more street segments; andprovide visible data indicating the geo-coordinates of the plurality ofoffsets in the user interface presented with the visible indicia of theelectronic map displayed via the display device.
 13. The apparatus ofclaim 9, wherein prior to the connecting of the portion, the memory andcomputer program code are further configured to, with the processor,cause the apparatus to determine a latitude coordinate and a longitudecoordinate of each offset point of the plurality of offset points. 14.The apparatus of claim 9, wherein the memory and computer program codeare further configured to, with the processor, cause the apparatus togenerate a dispatch plan for the one or more logistics zones based inpart on the trace order, the dispatch plan indicating a service sequencein which to pickup or deliver the items to addresses of the one or morelogistics zones.
 15. The apparatus of claim 9, wherein the memory andcomputer program code are further configured to, with the processor,cause the apparatus to generate one or more handling instructions basedin part on analyzing the trace order, the one or more handlinginstructions specifying a location in which one or more of the itemassociated with the route are assigned for placement in the vehicle or aposition in which the items are designated for placement in a hubfacility.
 16. The apparatus of claim 9, wherein the memory and computerprogram code are further configured to, with the processor, cause theapparatus to determine a work measurement time for delivery or pickup ofpackages within an area corresponding to the one or more logistics zonesbased in part on calculating a time to walk from the vehicle torespective doors of buildings corresponding to addresses.
 17. A computerprogram product comprising at least one non-transitory computer-readablestorage medium having computer-executable program code instructionsstored therein, the computer-executable program code instructionscomprising: program instructions configured to cause presentation of anelectronic map of a user interface; program instructions configured toreceive an indication that a user has provided a lasso gesture around ageographical area within the electronic map of the user interface;program instructions configured to in response to the receiving of theindication, cause generation, at the user interface, of an indicatorrepresenting a geofence around the geographical area; programinstructions configured to generate, at the user interface, one or morenodes for presentation within the indicator representing the geofencebased at least in part on the lasso gesture, wherein no nodes arepresented at the user interface in any area outside of the indicatorrepresenting the geofence, each of the one or more nodes is a visualindicator within the electronic map indicative of a connection pointbetween one or more street segments; program instructions configured toin response to the generating of the one or more nodes, generate, at theuser interface, a plurality of offset points based on assigning apredefined offset distance from the one or more street segments, eachoffset point, of the plurality of offset points, being located, at theuser interface, outside of a corresponding street segment of the one ormore street segments; program code instructions configured to based atleast in part on causing a visible connection, at the user interface, ofthe plurality of offset points automatically generate, at the userinterface, one or more logistics zones, each boundary of each logisticszone being defined, at the user interface, by a respective set of offsetpoints, of the plurality of offset points; in response to theautomatically generating the one or more logistics zones, program codeinstructions configured to generate, at the user interface and in eachlogistics zone of the one or more logistics zones, a geofenced rightzone on a right side of a corresponding street segment and a geofencedleft zone on a left side of the corresponding street segment; and basedat least in part on the generating of the geofenced left zone and thegeofenced right zone, automatically generating, a travel route for avehicle to travel for delivery or pickup of one or more items within anarea corresponding to the geofenced right zone and the geofenced leftzone.
 18. The computer program product of claim 17, further comprisingprogram code instructions configured to determine planned travel milesof the route based in part on calculating distances of each of the oneor more street segments in response to analyzing items of street segmentattribute data.